Open topic with left hand navigation
In the Portfolio work area, you can set permissions for security roles and company roles.
| Security Setting | Applies to Security Roles - Yes (Y)/No (N) | Applies to Company Roles - Yes (Y)/No (N) |
|---|---|---|
| Accounts | Y | Y |
| ACR | Y | Y |
|
Company# |
Y | Y |
|
Contact# |
Y | Y |
|
Custom Print Layout Document |
Y | Y |
| Distribution List | ||
|
External Report |
Y | Y |
| Lookup Management | Y | |
| Manage Web Service Queries | Y | Y |
| Problem | N | N |
| Procedure | N | N |
| Portfolio Properties | Y | Y |
| Project Team Roles | Y | Y |
|
Reading |
N | N |
| Resolution | N | N |
| Review Process | N | N |
|
Security Permissions* |
Y | Y |
| Shared Custom Print Layout Document | Y | Y |
| Shared Views | Y | Y |
| Specification | N | N |
| User Defined Lookup Management | N | N |
+ACR is not an actual document type. This setting controls whether a user can view and print the Anticipated Cost Report.
Note: If BCM integration has been disabled in the workspace, then the ACR will not display, regardless of its permission setting here. For more information, see "Enabling/Disabling BCM Integration".
#Companies and Contacts: Without permission to read companies and contacts, users are very restricted in Proliance. For users to perform even basic actions, such as forwarding documents or selecting recipients for collaboration, their security role must have read permission to companies and contacts.
*Security Permissions is not an actual document type. Rather, it represents all the security-related registers: Roles, Categories, and Company Roles. For more information, see "Restricting Access to Security".